Data processing apparatus and control method thereof with updating of unique identification information of a changed recorded file

ABSTRACT

A data recording apparatus holds device state information which is updated according to use of the apparatus and represents a use state of the apparatus, and device identification information unique to the apparatus. Upon recording data, the data recording apparatus acquires information associated with generation of recording data, which is different from the device state information, as recording information, in association with the recording data. The apparatus generates unique identification information of the recording data based on the device identification information, the device state information, and the recording information, and records a file including the recording data and the unique identification information in a recording medium.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a data processing apparatus, and acontrol method thereof.

2. Description of the Related Art

In general, in a digital camera, shot image data obtained by shooting isassigned a file name according to the rule of DCF (Design rule forCamera File system), for example, a file name IMG_XXXX.jpg (XXXX is anumeral which increments in the shooting order). However, when filesnamed by such a naming rule are copied to and managed by an externaldevice, file names often are not unique. In such a state, when a file iscopied to an external device, an old file may be overwritten.

For this reason, a technique for associating unique identificationinformation (to be referred to as unique ID hereinafter) used to specifyan image so as to improve image searchability and management between adigital camera and external device to which the digital camera isconnected has been proposed. Such association between the image andunique ID is executed on the digital camera side upon recording an imageor the like. Japanese Patent Laid-Open No. 2004-112602 has proposed adigital camera which calculates a unique ID based on a file path ofdata, and manages the data. Also, Japanese Patent Laid-Open No.2002-259332 has proposed a technique for recording identificationinformation unique to a device in data.

Furthermore, Japanese Patent Laid-Open No. 2002-271672 describes atechnique which acquires identification information unique to a deviceand image information from another electronic device, generates imageinformation that describes the identification information, and outputsthat image information. Japanese Patent Laid-Open No. 2002-259668discloses a technique which generates and outputs an image file whichdescribes an identifier of an electronic device itself, and a techniquewhich generates and outputs an image file that describes an identifierset by the user.

However, since the technique of Japanese Patent Laid-Open No.2004-112602 calculates a unique ID based on the file path of data,identical data that have different file path configurations will beassigned unique IDs. That is, a plurality of unique IDs may be assignedto identical image information. Since the technique of Japanese PatentLaid-Open No. 2002-259332 associates the unique ID of the device todata, the device can be specified from the data, but the data cannot beuniquely specified.

Furthermore, the technique described in Japanese Patent Laid-Open No.2002-271672 contemplates setting of the unique ID for image information,but does not contemplate the re-setting of a unique ID for an image thathas already been set with the unique ID. For example, when an editoperation is made to change the image contents, if the unique ID ismaintained even though the image information has changed, the sameunique ID is assigned to different images. Also, when processing such asrotation of an image that does not practically change the image contentsis applied, if the unique ID is re-assigned, a plurality of unique IDsare assigned to an identical image. The technique described in JapanesePatent Laid-Open No. 2002-259668 can specify the electronic device butcannot specify an image, and does not assume assignment of unique IDsupon image editing.

Therefore, with the general unique ID assignment method to imageinformation, identical data may be transferred a plurality of times withan external device that manages the holding state of image filesrecorded in the digital camera. Also, an image file that requirestransfer may fail to transfer. As a result, image file managementefficiency and reliability of the digital camera and external device areimpaired. The same issue applies to still image files, moving imagefiles, or audio files. That is, it is required to prevent identical datafrom being transferred a plurality of times with an external devicewhich manages the reception state of data files recorded in a recordingapparatus using the unique IDs of data files.

SUMMARY OF THE INVENTION

The present invention has been made in consideration of theaforementioned problems, and one feature of the present invention allowsassignment of unique identification information that does not cause anyduplication to data files.

Another feature of the present invention allows implementation ofefficient and highly reliable management that manages the receptionstate of data files using the unique IDs of the files.

According to one aspect of the present invention, there is provided adata processing apparatus comprising:

holding means configured to hold device state information which isupdated according to use of the data processing apparatus and representsa use state of the apparatus, and device identification informationunique to the apparatus;

acquiring means configured to acquire information associated withgeneration of recording data, which is different from the device stateinformation, as recording information, in association with the recordingdata;

generating means configured to generate unique identificationinformation of the recording data based on the device identificationinformation, the device state information, and the recordinginformation; and

recording means configured to record a file including the recording dataand the unique identification information generated by the generatingmeans in a recording medium.

According to another aspect of the present invention, there is provideda method of controlling a data processing apparatus, comprising:

a holding step of holding device state information which is updatedaccording to use of the data processing apparatus and represents a usestate of the apparatus, and device identification information unique tothe apparatus;

an acquiring step of acquiring information associated with generation ofrecording data, which is different from the device state information, asrecording information, in association with the recording data;

a generating step of generating unique identification information of therecording data based on the device identification information, thedevice state information, and the recording information; and

a recording step of recording a file including the recording data andthe unique identification information generated in the generating stepin a recording medium.

Further features of the present invention will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing an arrangement of a digital camera;

FIG. 2 is a flowchart showing an overall operation of a digital camera100;

FIG. 3 is a flowchart showing an shooting sequence of the digital camera100;

FIG. 4 shows an example of the configuration of a still image filerecorded in a recording medium 200;

FIG. 5 shows an example of the file structure recorded in the recordingmedium 200;

FIG. 6 is a flowchart showing a recording sequence of the digital camera100 for the recording medium 200;

FIG. 7 shows an example of directory entries recorded in the recordingmedium 200;

FIG. 8 is a flowchart showing a playback sequence of the digital camera100;

FIG. 9 is a flowchart showing a rotation processing sequence of thedigital camera 100;

FIG. 10 is a flowchart showing a still image edit sequence of thedigital camera 100;

FIG. 11 is a flowchart showing a reception processing sequence of thedigital camera 100;

FIG. 12 is a flowchart showing a rotation processing sequence of thedigital camera 100;

FIG. 13 shows an example of the configuration of an audio file recordedin the recording medium 200;

FIG. 14 is a flowchart showing an audio additional recording sequence ofthe digital camera 100;

FIG. 15 is a flowchart showing a head generation processing sequence ofthe digital camera 100;

FIG. 16 is a flowchart showing a moving image recording sequence of thedigital camera 100;

FIG. 17 shows an example of the configuration of a moving image filerecorded in the recording medium 200;

FIG. 18 is a flowchart showing a moving image edit sequence of thedigital camera 100; and

FIG. 19 is a block diagram showing an example of the functionalarrangement for generating a unique ID in a system controller 17.

DESCRIPTION OF THE EMBODIMENTS

Preferred embodiments of the present invention will now be described indetail in accordance with the accompanying drawings.

In the embodiments to be described hereinafter, a case will beexemplified wherein the present invention is applied to an image pick upapparatus (to be referred to as a digital camera hereinafter) which canrecord (shoot) a still image and moving image, and can record an audiosignal.

First Embodiment Description of Image Pick Up Apparatus

FIG. 1 is a block diagram showing an example of the arrangement of adigital camera 100 according to this embodiment. The digital camera 100serves as an image recording apparatus which records data of stillimages and moving images, and as an image playback apparatus whichdisplays images based on these data, and is an example of a dataprocessing apparatus to which the present invention is applicable.Referring to FIG. 1, an optical system 21 includes a shooting lens, andforms an optical image on an image capturing plane of an image sensingunit 22. The image sensing unit 22 comprises a CCD, CMOS element, or thelike, and converts an optical image into an electrical signal. An A/Dconverter 23 converts an analog image signal output from the imagesensing unit 22 into a digital signal, and converts an analog audiosignal output from an audio controller 11 into a digital signal.

A timing generator 12 supplies clock signals and control signals to theimage sensing unit 22, the audio controller 11, the A/D converter 23,and a D/A converter 13. The timing generator 12 is controlled by amemory controller 15 and system controller 17. An image processor 24applies predetermined pixel interpolation processing, resize processingsuch as reduction or the like, color conversion processing, and the liketo data from the A/D converter 23 or data from the memory controller 15.The image processor 24 makes predetermined arithmetic processing usingcaptured image data, and supplies the obtained arithmetic result to thesystem controller 17. The system controller 17 executes exposurecontrol, ranging control, and the like based on the arithmetic result.In this way, the system controller 17 executes TTL (through the lens) AF(auto focus) processing, AE (auto exposure) processing, and EF (flashpre-emission) processing. The image processor 24 executes predeterminedarithmetic processing using captured image data, and also executes TTLAWB (auto white balance) processing based on the obtained arithmeticresult.

The output data from the A/D converter 23 is written in a memory 32 viathe image processor 24 and memory controller 15 or directly through thememory controller 15. The memory 32 stores image files of still imagesand moving images obtained via the image sensing unit 22, and audiofiles of audio signals obtained via a microphone 10. The memory 32 alsostores file headers upon forming these image files and audio files. Thememory 32 has a storage capacity large enough to store a predeterminednumber of still images, and a moving image and audio signal of apredetermined period of time.

A compression/decompression unit 16 compresses/decompresses image databy adaptive discrete cosine transformation (ADCT) or the like. Thecompression/decompression unit 16 executes compression processing byreading a shot image which is stored in the memory 32 in the shootingprocessing started in response to pressing of, for example, a shutterbutton, and writes the processed data in the memory 32. Also, thecompression/decompression unit 16 executes decompression processing ofcompressed image data which is loaded from a recording medium 200 or thelike into the memory 32, and writes the processed data to the memory 32.The image data written in the memory 32 by the compression/decompressionunit 16 is converted into a file by the system controller 17, and thatfile is recorded in the recording medium 200 via an interface 18. Thememory 32 also serves as an image display memory, and image data fordisplay written in the memory 32 is displayed on an image display unit14 via the D/A converter 13. The image display unit 14 comprises, forexample, an LCD.

An audio signal output from the microphone 10 is supplied to the A/Dconverter 23 via the audio controller 11 which comprises an amplifierand the like, and is converted into a digital signal. The digital audiosignal is then stored in the memory 32 by the memory controller 15. Onthe other hand, audio data recorded in the recording medium 200 isloaded into the memory 32, and is then supplied to the audio controller11 via the D/A converter 13. The audio controller 11 drives aloudspeaker 81 in accordance with the audio signal from the D/Aconverter 13.

The system controller 17 controls the overall digital camera 100. Asystem memory 31 stores constants, variables, programs, and the likerequired for operations of the system controller 17. A nonvolatilememory 20 is an electrically erasable/recordable memory, and uses, forexample, an EEPROM or the like. The nonvolatile memory 20 stores controlprograms required for the system controller 17 to execute various kindsof control to be described later. The control programs stored in thenonvolatile memory 20 are loaded into the system memory 31 as needed,and are executed by the system controller 17. A shutter button 62,control panel 25, mode select button 27, and power button 39 areoperation buttons used by the user to input various operationinstructions to the system controller 17.

A first shutter switch signal SW1 is set ON at the middle pressing (halfstroke) position of the shutter button 62 provided to the digital camera100. Upon detection of the ON first shutter switch signal SW1, thesystem controller 17 starts the operations of the AF (auto focus)processing, AE (auto exposure) processing, AWB (auto white balance)processing, EF (flash pre-emission) processing, and the like. A secondshutter switch signal SW2 is set ON at the pressing completion (fullstroke) position of the shutter button 62. Upon detection of the ONsecond shutter switch signal SW2, the system controller 17 starts theoperations of a series of image capturing processes from when a signalis read from the image sensing unit 22 until image data is written inthe recording medium 200.

The control panel 25 comprises various buttons, a touch panel, and thelike. The control panel 25 includes, for example, an erase button, menubutton, SET button, arrow keys arranged in a cross pattern, and thelike. Upon pressing the menu button, a menu window that allows varioussettings is displayed on the image display unit 14. The user canintuitively make various settings using the menu window displayed on theimage display unit 14, and the arrow keys and SET button. The modeselect button 27 allows the user to switch the operation mode of thesystem controller 17 to one of a still picture mode, continuous shootingmode, moving image mode, playback mode, and the like. The power button39 is used to turn on/off the power supply of the digital camera 100.

A power supply controller 30 comprises a battery detection circuit,DC-DC converter, switch circuit that switches blocks to be energized,and the like, and detects the presence/absence of attachment of abattery, the type of battery, and the remaining battery capacity. Thepower supply controller 30 controls the DC-DC converter based on thedetection results and an instruction from the system controller 17, andsupplies required voltages to respective units including the recordingmedium 200 for required periods of time. A power supply unit 28comprises a primary battery such as an alkali battery, lithium battery,or the like, a secondary battery such as an NiCd battery, NiMH battery,Li battery, or the like, an AC adapter, and the like. Connectors 33 and34 connect the power supply unit 28 and power supply controller 30.

An RTC (Real Time Clock) 40 holds an internal power supply unitindependently of the power supply unit 28, and maintains a timepieceoperation state even when no electric power is supplied from the powersupply unit 28. The system controller 17 executes timer control using adate and time acquired from the RTC 40 upon startup.

An interface 18 is that with the recording medium 200. A connector 35connects the recording medium 200 and interface 18. A recording mediumattachment/detachment detector 38 detects whether or not the recordingmedium 200 is attached to the connector 35. The recording medium 200comprises a recording unit 19 comprising a semiconductor memory,magnetic disk, or the like, an interface 37 with the digital camera 100,and a connector 36 that connects the recording medium 200 and digitalcamera 100.

A communication unit 29 executes various kinds of communicationprocessing of RS232C, USB, IEEE1394, P1284, SCSI, modem, LAN, wirelesscommunication, and the like. A connector 63 (antenna in case of awireless communication) connects the digital camera 100 to anotherdevice via the communication unit 29.

<Description of Operation (Record Image File by Shooting)>

The operation of the digital camera 100 according to this embodimentwill be described below. Note that the processes to be describedhereinafter with reference to the accompanying flowcharts indicate thoseimplemented when the system controller 17 loads the control programsstored in the nonvolatile memory 20 onto the system memory 31, andexecutes them to attain arithmetic processing and control.

FIG. 2 is a flowchart for explaining the overall operation of thedigital camera 100 according to the first embodiment.

After the user presses the power button 39 to turn on the power supply,the system controller 17 initializes flags, control variables, and thelike in step S201. In step S202, the system controller 17 acquires thedate and time from the RTC 40, and makes settings for a system timer. Instep S203, the system controller 17 checks the setting state of the modeselect button 27. If a shooting mode is set by the mode select button27, the system controller 17 executes shooting mode processing in stepS204. Details of this shooting mode processing will be described laterwith reference to FIG. 3. On the other hand, if it is determined in stepS203 that the mode select button 27 is set in another mode other thanthe shooting mode, the process advances to step S205. In step S205, thesystem controller 17 executes processing according to the selected mode.Another mode includes, for example, a playback mode, communication mode,or audio recording mode. In the playback mode, image files recorded inthe shooting mode are played back and displayed. In the communicationmode, a communication is made with an external device via thecommunication unit 29 and connector 63 to exchange data. In the audiorecording mode, an audio signal input via the microphone 10 is recordedin association with an image.

Upon completion of the shooting mode processing or the processing of thecorresponding mode, the process advances to step S206. The systemcontroller 17 checks the setting position of the power button 39 in stepS206. If the power button 39 is set to the power ON position, theprocess returns to step S203. If it is determined in step S206 that thepower button 39 is set to the power OFF position, the process advancesto step S207 to execute end processing. In the end processing, forexample, the system controller 17 changes display on the image displayunit 14 to the end state, records parameters and setting valuesincluding the flags, control variables, and the like, and the set modein the nonvolatile memory 20, and shuts off the power supply to theunits which do not require any power supply after power OFF. Uponcompletion of the end processing, the system controller 17 ends theprocessing shown in FIG. 2.

The shooting mode processing (that in step S204 in FIG. 2) of thedigital camera 100 according to the first embodiment will be describedbelow. Note that the image capturing processing started upon pressing ofthe shutter button 62 in the shooting mode will be described below.

The first shutter switch signal SW1 is set ON at the half strokeposition of the shutter button 62. As described above, the systemcontroller 17 starts the operations of the AF processing, AE processing,AWB processing, EF processing, and the like in response to the ON firstshutter switch signal SW1. The second shutter switch signal SW2 is setON at the pressing completion (full stroke) position of the shutterbutton 62. The system controller 17 recognizes this operation as anoperation start instruction of a series of image capturing processes,and starts shooting (processing shown in FIG. 3).

Upon starting the shooting, in step S301 the system controller 17acquires the current value (date and time) from the timer set in stepS202 in FIG. 2, and holds it in the system memory 31. In steps S302 toS305, the system controller 17 executes shooting at a shutter speeddetermined by the AE processing. More specifically, the systemcontroller 17 opens a shutter in step S302 and starts exposure in stepS303. The system controller 17 checks in step S304 the end of exposurebased on the shutter speed (exposure time) determined by the AEprocessing executed while the first shutter switch signal SW1 is ON. Theshutter speed determined by the AE processing is saved in, for example,the system memory 31, and is acquired from there. If the end of exposureis determined, that is, if the exposure time corresponding to theacquired shutter speed has elapsed, the system controller 17 closes theshutter in step S305. In step S306, the system controller 17 reads out asignal (image signal) accumulated in the image sensing unit 22 by theshooting operation, converts it into digital data by the A/D converter23, and writes the digital data in the memory 32.

Subsequently, in step S307 the system controller 17 applies imageprocessing to the image data written in the memory 32 using the memorycontroller 15 and image processor 24. In step S308, thecompression/decompression unit 16 compresses the image data that hasundergone the image processing to generate compressed image data. Notethat the compressed image data is configured by various marker codes andcompressed data, as will be described later with reference to FIG. 4.

In step S309, the system controller 17 applies image processing for athumbnail to the image data that has undergone the image processing andis stored in the memory 32, using the memory controller 15 and imageprocessor 24, so as to obtain a thumbnail image. In step S310, thesystem controller 17 applies compression for a thumbnail to thethumbnail image, and stores the result in the memory 32. The image thathas undergone the compression for a thumbnail and is stored in thememory 32 will be referred to as “thumbnail” hereinafter.

In step S311, the system controller 17 generates an image file headermainly including shooting time information in the memory 32. The headergeneration processing in step S311 will be described later withreference to FIG. 15. In step S312, the system controller 17 calculatesthe sum of the data size of the compressed image data generated in stepS308, that of the thumbnail generated in step S310, and the header sizegenerated in step S311, and stores the sum in the system memory 31. Instep S313, the system controller 17 executes shot image recordingprocessing to be described later with reference to FIG. 6, thus endingthe processing shown in FIG. 3. Note that the recording processing instep S313 may be executed in synchronism with the aforementionedshooting sequence or asynchronously. In this way, the image file isgenerated and is written in the recording medium.

FIG. 4 shows an example of the data configuration of the image filegenerated by the processing in FIG. 3. An image file 401 generated bythe shooting processing has a marker SOI 402 indicating the start of theimage at the head of the file. The image file 401 has an applicationmarker (APP1) 403 after the SOI 402. The application marker 403includes:

-   -   APP1 Length 404 indicating the size of APP1;    -   APP1 Identifier Code 405 as an identification code of APP1;    -   Date Time 406 indicating the generation date and time of image        data;    -   Date Time Original 407 indicating the generation date and time        of original image data;    -   Etc 408 as miscellaneous shooting information;    -   Unique ID 418 as a file unique ID of the image file of interest;        and    -   thumbnail data Thumbnail Data 410 described above.

Upon generating the application marker 403 in step S311 (headergeneration processing), the Date Time 406 and Date Time Original 407store the shooting date and time information stored in the system memory31 in step S301.

The compressed image data generated in step S308 includes a quantizationtable (DQT) 412, Huffman table (DHT) 413, frame start marker (SOF) 414,scan start marker (SOS) 415, and compressed data 416. The compressedimage data is terminated by a marker (EOI) 417 indicating the end ofimage data.

FIG. 5 shows an example of the configuration of directories recorded inthe recording medium 200 as a result of the recording processing in stepS313. Under the root directory, a DCIM directory 501 is recorded, andsubdirectories each having a name generated using eight characters aregenerated under the DCIM directory 501. The name held by eachsubdirectory includes first three characters as a numeric part startingfrom 100, and a subdirectory name whose numeric part is incremented byone every time a new subdirectory is generated is assigned(subdirectories 502 and 503). Under the subdirectory 502, various files504 to 507, 509, and 519 generated by the digital camera 100 of thisembodiment are generated. Note that the file name to be generatedconforms to the following file name generation rule. That is, the filename includes a file name of eight characters, and an extension of threeletters indicating the type of file. Of the file name, the last fourcharacters are a numeral starting from 0001, and the numeral isincremented by one for each shooting, thus assigning a file name. Notethat “JPG” is assigned to an extension of a still image, “AVI” isassigned to that of a moving image, and “WAV” is assigned to that of anaudio signal.

FIG. 6 is a flowchart showing details of the recording processing (stepS313 in FIG. 3) for recording image data generated by the aforementionedshooting sequence in the recording medium.

When the recording processing starts, in step S601 the system controller17 generates a file name according to the aforementioned file namegeneration rule. The system controller 17 acquires the date and timeinformation stored in the system memory 31 in step S301 of the shootingsequence in step S602, and acquires the data size of the file to berecorded in step S603. Note that the data size of the file is calculatedin step S312.

After that, the system controller 17 checks in step S604 if a directorythat stores the generated file exists in the recording medium 200. Thisembodiment adopts a DCF directory which is standardized in a format of“/DCIM/xxxYYYY”: xxx is a directory number (a numerical character stringfrom 100 to 999), and YYYY is an ASCII character string. If the numberof files stored in a directory having a maximum directory number is lessthan an upper limit value, the system controller 17 determines thedirectory having the maximum directory number to be a storage locationof the generated file. In this case, the directory that stores thegenerated file exists on the recording medium 200. On the other hand, ifthe number of files stored in the directory having the maximum directorynumber is equal to or larger than the upper limit value or if nodirectory exists, the process advances to step S605 because no directorythat stores the generated file exists.

If no directory exists, the system controller 17 generates a directorythat stores the generated file (e.g., 100OANON (subdirectory 502)) instep S605, and the process advances to step S606. As the generationmethod of a directory name, a directory name having the maximumdirectory number +1 may be generated. On the other hand, if thedirectory already exists, the process jumps from step S604 to step S606.In step S606, the system controller 17 generates a directory entry usingthe file name generated in step S601 and the date and time informationacquired in step S602.

FIG. 7 is a view for explaining a directory entry. Directory entries 707to 710, 712, 717, and 713 to 716 entering a directory entry set 701respectively correspond to files 504 to 507, 509, 519, and 515 to 518 inthe example of the directory configuration shown in FIG. 5. The contentsof an extension field 702 are as has been described above using FIG. 5.In step S607, the system controller 17 records the value acquired instep S602 in a generation date and time field 703 and update date andtime field 704 in the directory entry set 701. Therefore, the same valueis described in the generation date and time field 703 and update dateand time field 704. Also, the system controller 17 records the data sizeof the image file stored in the system memory 31 in step S312 in a filesize field 706, and also a start cluster number indicating a free dataarea in the recording medium 200 (that of a data area where the imagefile of interest is stored) in a start cluster number field 705.

Upon completion of generation of the directory entry corresponding tothe file of interest, in step S607 the system controller 17 writes thedirectory entry generated in step S606 and the image data generated bythe shooting processing in the recording medium 200. The systemcontroller 17 then ends the recording processing.

<Description of Operation (Playback to Edit of Image File)>

The processing for generating a new file using the image file recordedin the recording medium 200 in the shooting mode will be describedbelow.

When the mode select button 27 is switched to the playback mode, thesystem controller 17 executes the playback processing for playing backimage files recorded in the recording medium 200 to have the datastructure described above using FIG. 5 on the image display unit 14. Theplayback processing will be described below with reference to FIG. 8.

Upon starting playback, in step S801 the system controller 17 acquiresthe file names of files to be played back with reference to thedirectory entry recorded in the recording medium 200. In step S802, thesystem controller 17 reads out the files to be played back from therecording medium 200 into the memory 32. In step S803, the systemcontroller 17 applies decompression processing to the read out filesusing the compression/decompression unit 16, and stores the decompressedimage data in the memory 32 again. The system controller 17 resizes thedecompressed image data stored in the memory 32 to a display size instep S804, and stores the resized image data in the memory 32 as VRAMdata in step S805. Finally, in step S806 the system controller 17outputs the VRAM data stored in the memory 32 to the image display unit14 via the memory controller 15 and D/A converter 13, thus displayingimages.

The user can sequentially determine the file names of files to be playedback from the directory entry using the arrow keys included in thecontrol panel 25. That is, the user sequentially selects image filesrecorded in the recording medium 200 using the arrow keys to apply theplayback process to the selected image files, and can browse the imagefiles in the recording medium 200 using the image display unit 14. Whilebrowsing, the rotation operations of images can be accepted. Therotation processing of an image between the landscape and portraitorientations will be described below with reference to FIG. 9. Uponacceptance of a rotation instruction at the control panel 25, the systemcontroller 17 starts the rotation processing shown in the flowchart ofFIG. 9 for an image which is being displayed on the image display unit14. Note that this embodiment implements the rotation operation bychanging “Orientation” (included in the shooting information Etc 408) asa rotation attribute of the file header. At this time, the systemcontroller 17 does not generate any file unique ID (Unique ID 418) andchanges only the rotation attribute (Orientation).

The system controller 17 acquires the file name of the file to berotated in step S901, and loads that file from the recording medium 200in step S902. In step S903, the system controller 17 decompresses theimage data using the compression/decompression unit 16, and stores thedecompressed image data in the memory 32. Upon acceptance of a rotationinstruction in step S904, the system controller 17 executes headergeneration processing to be described later with reference to FIG. 15 toupdate the rotation attribute (Orientation) in step S905. In step S906,the system controller 17 writes the result in the recording medium 200.As will be described later with reference to FIG. 15, the headergeneration processing executed in step S905 does not generate any fileunique ID but changes only the rotation attribute.

The digital camera 100 of this embodiment allows the user to executeedit processing for applying image size conversion to an image filedisplayed on the image display unit 14 and recording a new image file.This processing will be described below with reference to FIG. 10.

Upon starting the edit processing, in step S1001 the system controller17 selects image data displayed on the image display unit 14 as data tobe edited, and acquires its file name. Assume that the file name of thefile to be edited is IMG_(—)0002.JPG. In step S1002, the systemcontroller 17 loads image data recorded in the recording medium 200 andits directory entry into the memory 32 based on the file name acquiredin step S1001. In step S1003, the system controller 17 decompresses theimage data using the compression/decompression unit 16, and stores thedecompressed image data in the memory 32. In step S1004, the systemcontroller 17 executes enlargement/reduction processing to apredetermined image size to the decompressed image data, and stores thesize-changed image in the memory 32. In step S1005, the systemcontroller 17 applies compression processing to the size-changed image,and stores the result in the memory 32.

In step S1006, the system controller 17 acquires the contents of thegeneration date and time field 703 in the directory entry of the imagefile loaded in step S1002, and recognizes the acquired date and time asa shooting date and time. In step S1007, the system controller 17acquires the current date and time from the system timer set in stepS202. In step S1008, the system controller 17 generates a header inassociation with the size-changed image data. The header generationprocessing will be described in detail later with reference to FIG. 15.In the header generation processing in step S1008, the system controller17 copies the header part of the original image data loaded into thememory 32, and updates items associated with the image size andgeneration date and time in the copied header part. That is, the systemcontroller 17 updates a field associated with the image size in thecopied header part, and changes the field of the item Date Time 406associated with the generation date and time to the acquired currentdate and time. Also, the system controller 17 assigns a new file uniqueID.

With the aforementioned processing, generation of new image data iscomplete. The system controller 17 generates a file name of the newimage data to be generated in step S1009, and generates (edits) thedirectory entry using that file name in step S1010. In this example,assume that a file name IMG_(—)0003.JPG is generated, and a directoryentry 709 is generated. At this time, the system controller 17 sets thegeneration date and time of the original image acquired in step S1006 inthe generation date and time field 703, and sets the current date andtime acquired in step S1007 in the update date and time field 704 of thedirectory entry corresponding to the file. In step S1010, the systemcontroller 17 sequentially generates the file size to be generated, andthe start cluster number of the recording medium 200 that records imagedata. After the system controller 17 generates a directory entry in thisway, it writes the size-changed image data and its directory entry inthe recording medium in step S1011. In this way, the system controller17 ends the edit processing.

Upon acquiring the shooting date and time of an original image in stepS1006, it is often apparently determined that the shooting dates andtimes are not correctly set (e.g., “0” is set in the generation date andtime fields 703 of the directory entries). In such case, the systemcontroller 17 may acquire the contents of the update date and time field704 in the directory entry of the original image. Likewise, the systemcontroller 17 may use the Date Time Original 407 described in the fileheader of the original image for the shooting date and time.

<Reception Processing>

Upon switching the mode select button 27 to the communication mode, thesystem controller 17 executes reception processing shown in FIG. 11. Inthe reception processing, the system controller 17 checks in step S1101if a communication partner is found (if an external device which isconnected to allow communications is found). If it is determined that acommunication partner is not found, the system controller 17 ends thisprocessing. If a communication partner is found, the system controller17 checks in step S1102 if a transmission request from the communicationpartner is detected. If no transmission request is detected, the processreturns to step S1101 to repeat confirmation of the presence/absence ofa communication partner and that of a transmission request. On the otherhand, if a transmission request is detected, the process advances tostep S1103. In step S1103, the system controller 17 receives data fromthe communication partner via the communication unit 29, and temporarilyholds the received data in the memory 32. The data that can be receivedincludes a still image file, moving image file, and audio file. In stepS1104, the system controller 17 writes the received data in therecording medium by the aforementioned recording processing. Therefore,the processing shown in FIG. 6 includes not only recording of imagefiles (still image files and moving image files) but also that of audiofiles. Upon completion of the recording processing, the process returnsto step S1101 to confirm the presence/absence of a communication partneragain, and to wait for a transmission request again. At this time, theheader generation processing is not executed, that is, a new file uniqueID is not issued. That is, upon storing a file received from an externaldevice in the recording medium, unique identification information isinhibited from being updated.

<Audio Processing>

Upon switching the mode select button 27 to the audio recording mode,the system controller 17 executes audio recording processing shown inFIG. 12.

Upon detection of an instruction for the start of audio recording fromthe control panel 25 in the audio recording mode, the system controller17 acquires the current date and time from the system timer in stepS1201, and generates a file name of a file used to record an audiosignal in step S1202. The file name generation method is as has beendescribed above using FIG. 5. In step S1203, the system controller 17begins to capture audio data. An audio signal is input from themicrophone 10, and is stored as audio data in the memory 32 via theaudio controller 11 and A/D converter 23. This embodiment assumesdigital data in a PCM format as the audio data. FIG. 13 shows thestorage format of audio data at this time. At the head part of data, afixed-length header field 1301, which includes audio sampling rates,file unique ID (Unique ID 1302), and the like, is allocated. Immediatelyafter the header field 1301, a fixed-length audio data field 1303, whichstores audio data for 1 sec, is allocated. Fixed-length audio data for 1sec is enumeration of audio data 1304, 1305, and 1306 according to thesampling rates.

Upon completion of storage of the data for 1 sec, in step S1204 thesystem controller 17 starts recording processing of the audio datastored in the memory 32 in the recording medium 200 in parallel with tothe audio recording processing. By repeating steps S1203 and S1204 untilan instruction for the end of recording is detected, audio data iscontinuously recorded. Upon detection of the instruction for the end ofrecording from the control panel 25, the process advances from stepS1205 to step S1206, and the system controller 17 executes the headergeneration processing to be described later with reference to FIG. 15.In step S1207, the system controller 17 writes the header generated bythe header generation processing in the recording medium 200 as theheader field 1301. In step S1208, the system controller 17 generatesdirectory entry information based on the date and time informationacquired in step S1201, the file name generated in step S1202, and thefinal file size. In step S1209, the system controller 17 writes thegenerated information in the recording medium 200, thus ending the audiorecording processing.

Upon detection of an instruction for the start of additional audiorecording from the control panel 25 in the audio recording mode, thesystem controller 17 starts additional audio recording processing shownin FIG. 14.

Upon starting the additional recording processing, the system controller17 acquires the audio data file name which is to undergo additionalrecording in step S1401, and acquires its directory entry in step S1402.For example, the system controller 17 acquires the directory entry 717in the directory entry set 701 in FIG. 7. Furthermore, the systemcontroller 17 acquires the contents of the generation date and timefield 703 in the entry that records the shooting date and time, andholds it in the system memory 31 in step S1403. In step S1404, thesystem controller 17 loads audio data which is to undergo additionalrecording from the recording medium 200 based on the entry information,analyzes the loaded data to acquire header information, and holds theheader information in the system memory 31. At this time, in step S1405the system controller 17 calculates and determines the additionalrecording start position.

In step S1406, the system controller 17 stores audio data input from themicrophone 10 in the memory 32 via the audio controller 11 and A/Dconverter 23 as in the audio recording processing. The data format inthis processing assumes digital data in the PCM format described above.

Upon completion of storage of data for 1 sec, the system controller 17starts additional recording processing of the audio data stored in thememory 32 to the recording medium 200 in step S1407 in parallel with tothe audio recording processing. By repeating steps S1405 to S1407, audiodata can be continuously additionally recorded.

Upon detection of an instruction for the end of additional recording viathe control panel 25, the process advances from step S1408 to stepS1409, and the system controller 17 executes the header generationprocessing to be described later with reference to FIG. 15. In stepS1410, the system controller 17 generates the header field 1301 usingthe data generated in step S1409, appends it to the additionallyrecorded audio data, and writes the audio data in the recording medium200 as an audio file. Furthermore, in step S1411 the system controller17 generates directory entry information based on the date and timeinformation acquired in step S1403, the file name acquired in stepS1401, and the final file size. In step S1412, the system controller 17writes the directory entry information in the recording medium 200, thusending the audio additional recording processing.

<Header Generation Processing>

FIG. 15 is a flowchart for explaining the header generation processingaccording to this embodiment. FIG. 19 is a block diagram showing anexample of the function arrangement required to generate a unique ID inthe system controller 17. The header generation processing in step S311in FIG. 3, step S905 in FIG. 9, step S1008 in FIG. 10, step S1206 inFIG. 12, and step S1409 in FIG. 14 will be described below withreference to FIGS. 15 and 19.

The system controller 17 checks in step S1501 if an operation to a fileis an edit operation of a predetermined attribute (e.g., rotationattribute (Orientation) or the like) described in a predetermined headerof the file. If that operation is an edit operation of a predeterminedattribute (e.g., S905 in FIG. 9), the system controller 17 changes onlythe predetermined attribute to be edited in step S1510, thus ending thisprocessing. That is, if there is no practical change for image data, thesystem controller 17 changes only the predetermined attribute to beedited to update the header, and obtains a header after the editoperation. In other words, upon making the edit operation for changingonly attribute information described in the file header in associationwith the file recorded in the recording medium, unique identificationinformation is inhibited from being updated.

On the other hand, if the operation to the file is not the editoperation of only information described in the header, for example, ifthe operation to the file is creation of a new file, or an editoperation for changing main body data (image data or audio data) in thefile, the process advances from step S1501 to step S1502. In step S1502,the system controller 17 acquires recording information 1901. Therecording information 1901 includes parameter information of shooting oraudio recording such as a recording date and time 1902, recordingparameter information 1903, and the like, which correspond to the file.Note that the recording date and time 1902 is a shooting date (shootingyear, month, day) and shooting time (shooting hour, minute, second)generated based on the date and time acquired from the RTC 40. Also, therecording parameter information 1903 includes, for example, controlinformation (f-number/shutter speed/exposure correction value/whitebalance information, etc.) upon shooting. That is, the recordinginformation 1901 is associated with the generation condition of therecording data of interest independently of device state information1904 to be described later.

The system controller 17 checks in step S1503 if a new header is to begenerated. If a new header is to be generated, the system controller 17generates a header by describing the acquired recording information inaccordance with a predetermined format in step S1504. On the other hand,if the header has already been generated, since the recordinginformation has already been described, the system controller 17 skipsthe processing in step S1504. Note that it is determined that a newheader is to be generated when new image data is recorded (S311 in FIG.3) or new audio data is recorded (S1206 in FIG. 12). Also, it isdetermined that the header has already been generated upon execution ofthe image edit operation for changing the size or the like (S1008 inFIG. 10) or upon additionally recording audio data (S1409 in FIG. 14).

In step S1505, the system controller 17 acquires device stateinformation 1904 from the nonvolatile memory 20. The device stateinformation 1904 is information which represents the states of deviceuse such as a recording count (a shooting count for image data and anaudio recording count for audio data), data generation count, dataupdate count, shutter operation count, and the like, which are updatedaccording to the use of the device. In step S1506, the system controller17 acquires a device unique ID 1905 from the nonvolatile memory 20. Thedevice unique ID is an ID such as a serial number upon manufacture, MACaddress (Media Access Control address) of the device, or the like, whichspecifies the device. Note that the device unique ID 1905 may be storedin a ROM (not shown) or the like. In step S1507, a unique ID generationunit 1906 generates a file unique ID 1907 based on the recordinginformation 1901, device state information 1904, and device unique ID1905, which are acquired in steps S1502, S1505, and S1506. In stepS1508, the system controller 17 describes the file unique ID 1907 at apredetermined location of the header (Unique ID 418). Note that the fileunique ID 1907 may be generated by enumerating the recordinginformation, device state information, and device unique ID, or byarithmetic operations of the respective pieces of information. In stepS1509, the system controller 17 updates the acquired and used devicestate information, and stores the updated information in the nonvolatilememory 20, thus ending this processing.

In the above example, the device state information is updated at theheader generation timing. As the holding/update timing of the devicestate information, the system controller 17 stores information read outfrom the nonvolatile memory 20 upon startup in the system memory 31. Thesystem controller 17 increments by one the device state informationstored in the system memory 31 at the header generation timing, andwrites out the device state information stored in the system memory 31to the nonvolatile memory 20 upon system shutdown. Of course, the systemcontroller 17 may write out the device state information to thenonvolatile memory 20 every time it updates the information.

When the device state information includes a shutter count, it isupdated every time an image is shot. Using this information, an IDunique to an image file can be generated. When the device stateinformation includes a recording count, it can be updated every timedata is generated and recorded in the recording medium. For this reason,a file unique ID can be generated not only for an image file but alsofor a file such as an audio file or the like, which can be recordedirrespective of shutter control. When the device state informationincludes a data generation count, it is updated not only when data isgenerated and recorded in the recording medium but also when thegenerated data is transmitted to another device such as a PC or the likewithout being recorded in the recording medium. When the device stateinformation includes a data update count, it can be updated when thegenerated data is partially changed, or when the data is added ordeleted. Hence, a unique file ID can be generated. Note that acombination of two or more types of device state information may beused.

As described above, according to this embodiment, a unique file ID canbe appended to data to be recorded throughout a plurality of devices, aplurality of recording media, and a plurality of data. Since the uniqueID is generated using the recording information, device stateinformation, and device unique ID, ID generation can be sped up.

According to this embodiment, when a data file is transferred from anexternal device, no new unique file ID is assigned to that file. Forthis reason, identical data can be prevented from being transferred aplurality of times with a host that manages the reception state of datafiles recorded in the external device using unique device IDs. Uponediting the header, since a new unique device ID is not assigned,generation of an unwanted unique ID due to a simple change in attributesuch as a change in rotation information or the like can be prevented.When the contents of data are changed, since a unique file ID is issuedagain, data management using the unique file IDs can be easily made withhigh reliability.

Second Embodiment

In the first embodiment, still image recording and audio recording havebeen described. The digital camera 100 can also make moving imagerecording in addition to the still image recording. The moving imagerecording can be executed by selecting the moving image recording modeby the mode select button 27. The operation of the digital camera 100 inthe moving image recording mode will be described below.

Upon detection of the ON second shutter switch signal SW2 in the movingimage recording mode, the system controller 17 sequentially stores imagedata captured by the image sensing unit 22 in the memory 32 at apredetermined frame rate. At the same time, the system controller 17stores an audio signal captured from the microphone 10 in the memory 32via the audio controller 11 and A/D converter 23.

The moving image mode processing according to the second embodiment willbe described below with reference to FIG. 16. This processing isexecuted when the moving image mode is determined in, for example, stepS203 of FIG. 2.

Upon detection of the ON second shutter switch signal SW2 in the movingimage recording mode, the system controller 17 starts the moving imagerecording processing shown in FIG. 16. In step S1601, the systemcontroller 17 sequentially stores image data captured by the imagesensing unit 22 in the memory 32 at a predetermined frame rate. At thesame time, the system controller 17 stores an audio signal captured fromthe microphone 10 in the memory 32 via the audio controller 11 and A/Dconverter 23. The second embodiment assumes digital data in a PCM formatas audio data. In step S1602, the system controller 17 executes imageprocessing for, for example, converting the image data stored in thememory 32 into an image size to be recorded in a moving image file. Instep S1603, the system controller 17 applies compression processing tothe image data, and stores the compressed image data in the memory 32.

FIG. 17 shows the storage format of a moving image file to be recordedin the recording medium 200. At the head position of data, afixed-length header field 1701 which includes data such as a video framerate, audio sampling rate, and the like is allocated. Immediately afterthe header field 1701, a fixed-length audio data field 1702 that storesaudio data for 1 sec is allocated. Audio data input from the microphone10 is sampled to digital data via the audio controller 11 and A/Dconverter 23, and the digital data is stored in the memory 32.Immediately after the audio field 1702, frame data recorded at thepredetermined frame rate are sequentially stored in the memory 32 (data1703 to 1706) to generate sequential data in increments of 1 sec.

Upon completion of storage of data for 1 sec, in step S1604 the systemcontroller 17 starts processing for recording moving image data storedin the memory 32 in the recording medium 200 in parallel with to therecording processing of the moving image data and audio data. Note thatthe recording processing in step S1604 will be described later. Thesystem controller 17 repeats these processes (S1601 to S1604) until itdetects a moving image stop request in step S1605. Upon re-detection ofthe second shutter switch signal SW2, detection of exhaustion of thefree capacity of the recording medium 200, or detection of exhaustion ofthe free space of the memory 32, a moving image stop request isgenerated.

The configuration of the directories recorded in the recording medium200 by the recording processing is as has been described above usingFIG. 5. Under the root directory, the DCIM directory 501 is recorded,and subdirectories each having a name generated using eight charactersare generated under the DCIM directory 501. The name held by eachsubdirectory includes first three characters as a numeric part startingfrom 100, and a subdirectory name is assigned whose numeric part isincremented by one every time a new subdirectory is generated (e.g.,subdirectories 502 and 503 in FIG. 5). Under the subdirectory 502,various files (e.g., files 511 to 518 in FIG. 5) generated by thedigital camera 100 of the second embodiment are generated. The file nameto be generated includes a file name of eight characters, and anextension of three letters indicating the type of file. Of the filename, the last four characters are a numeral starting from 0001, and thenumeral is incremented by one for each shooting, thus assigning a filename in the still image recording mode. Note that “JPG” is assigned toan extension of a still image. Also, “AVI” is assigned to that of amoving image recorded in the moving image mode (e.g., files 515 and517), and “THM” is assigned to that of a thumbnail file that recordsmanagement information (e.g., files 516 and 518). Note that thethumbnail is generated in step S1609 to be described later.

The recording processing (step S1604) of the second embodiment issimilar to that of the first embodiment. Therefore, the recordingprocessing of the second embodiment will be described below using FIG.6. When the recording processing starts, in step S601 the systemcontroller 17 generates a file name. In this case, the system controller17 generates a file name, for example, MVI_(—)0005.AVI since the movingimage recording mode is selected. The system controller 17 acquires fromthe system memory 31 the date and time at the beginning of recording instep S602, and acquires the write size in step S603. Note that, the dateand time at the beginning of recording have been obtained from thesystem timer and stored in the system memory 31 in the step S1601. Thetime at the beginning of recording is also referred to as the shootingdate and time.

Upon execution of the first write process (i.e., the write process ofdata including the header field 1701), the system controller 17 checksthe presence/absence of a directory that stores the generated file instep S604. If the corresponding directory is not found, the systemcontroller 17 generates a directory in step S605, and the processadvances to step S606. On the other hand, if the corresponding directoryis found, the process jumps from step S604 to step S606. The systemcontroller 17 generates a directory entry in that directory in stepS606, and writes data in the recording medium 200 in step S607. In thesecond and subsequent write processes, since the problem of thedirectory has already been solved, the system controller 17 writes datain the directory in which the data is written in the first writeprocess.

When the moving image recording processing stops, the process advancesfrom step S1605 to step S1606. In step S1606, the system controller 17writes remaining moving image data in the memory 32, and records indexinformation 1718 that stores offsets to respective audio data/video dataand sizes. In step S1607, the system controller 17 generates headerinformation including the total number of frames and the like. In stepS1608, the system controller 17 describes the total data size in thedirectory entry, and records that information in the recording medium200, thus completing recording of the moving image file. In step S1609,the system controller 17 generates management information of the movingimage file as a file MVI_(—)0005.THM (directory entry 714) having thesame number as the above moving image file name.

The thumbnail file generated in this step has the same structure as theimage data file shown in FIG. 4. That is, thumbnail data has a markerSOI 402 indicating the start of the image at the head of the file. Thethumbnail data has an application marker (APP1) 403 after the SOI 402.The application marker 403 includes:

-   -   APP1 Length 404 indicating the size of APP1;    -   APP1 Identifier Code 405 indicating an identification code of        APP1;    -   Date Time 406 indicating the generation date and time of image        data;    -   Date Time Original 407 indicating the generation date and time        of original image data; and    -   Etc 408 as miscellaneous shooting information.

Note that the thumbnail file does not include any thumbnail imageThumbnail Data 410.

Upon generating thumbnail data in step S1609, the system controller 17stores the shooting date and time information stored in the systemmemory 31 in the aforementioned Date Time 406 and Date Time Original407. Note that the shooting date and time information is stored in thesystem memory 31 in step S1601.

The thumbnail image is a reduced-scale image of the first frame at thebeginning of moving image recording, and includes a quantization tableDQT 412, Huffman table DHT 413, frame start marker SOF 414, scan startmarker SOS 415, and compressed data 416 (compressed data of thethumbnail image). The thumbnail image is terminated by a marker EOI 417indicating the end of image data.

The thumbnail generation processing in step S1609 will be describedbelow. Upon starting the thumbnail generation, the system controller 17applies image processing for, for example, converting the first framestored in the memory 32 to a predetermined image size. The systemcontroller 17 executes compression processing using thecompression/decompression unit 16, generates a header including theapplication marker 403 described above, and writes data in the recordingmedium. After the thumbnail file is generated in this way, the systemcontroller 17 ends the moving image recording processing in FIG. 16.

The moving image data generated by the above processing can undergoclipping edit processing after a predetermined frame by the digitalcamera 100 of this embodiment. A description about storage of a new fileof moving image data obtained by applying backward clipping editprocessing to the file MVI_(—)0005.AVI (directory entry 713) will begiven using FIG. 18.

Upon starting the edit processing, in step S1801 the system controller17 acquires the clipping start position in the moving image selected bythe arrow buttons of the control panel 25, and settles the clippingstart position in the moving image file shown in FIG. 17 based on theselected frame. Next, in step S1802 the system controller 17 acquiresthe file name of an original moving image file to be edited. In thiscase, assume that the file name to be acquired is MVI_(—)0005.AVI. Instep S1803, the system controller 17 acquires the correspondingdirectory entry (e.g., directory entry 713 in FIG. 7). In step S1804,the system controller 17 acquires the contents of the generation dateand time field 703 in the acquired directory entry, that records theshooting date and time, and holds it in the system memory 31. In stepS1805, the system controller 17 acquires the current date and time fromthe system timer as the edit start timing and stores it in the systemmemory 31. Subsequently, the system controller 17 loads moving imagedata from the recording medium 200 onto the memory 32 in step S1806, andrecords the loaded data in a new file in step S1807. The recordingsequence in this case is that shown in FIG. 6.

That is, the system controller 17 generates a new file name(MVI_(—)0006.AVI in this case) in step S601, acquires the date and timeat the beginning of recording (the edit start timing) from the systemmemory 31 in step S602, and acquires the write size in step S603. Uponexecution of the first write process (i.e., the write process of dataincluding the header field 1701), the system controller 17 checks instep S604 if a directory that stores the generated file exists. If thedirectory is not found, the process advances to step S605 to generate adirectory, and the process advances to step S606. On the other hand, ifit is determined in step S604 that the directory that stores thegenerated file is found, the process jumps to step S606. The systemcontroller 17 generates a directory entry (directory entry 715) in thatdirectory in step S606, and writes data in the recording medium 200 instep S607.

Subsequently, the system controller 17 checks in step S1808 if the dataloaded in step S1805 includes the edit start position stored in thesystem memory 31 in step S1801. The loading processing (step S1806) andrecording processing (step S1807) are continued until it is determinedin step S1808 that the edit start position is included. If dataincluding the edit start position is loaded in step S1806, the systemcontroller 17 records moving image data immediately before the editposition in the recording medium 200 and records index data accordinglyin the recording processing in step S1807. Upon completion of recordingof moving image data, in step S1809 the system controller 17 edits thecontents of the generation date and time field 703 in the directoryentry 715 based on the shooting date and time information of theoriginal moving image data stored in the system memory 31 in step S1804.The system controller 17 then writes it in the recording medium 200,thus ending the moving image edit processing in step S1810.

Upon completion of the above processing, the system controller 17 cangenerate management information of the moving image file in another fileMVI_(—)0006.THM. This file has the same structure as in FIG. 4 describedabove, and thumbnail data of the first frame 1703 of the moving imagedata is recorded as compressed data. Data based on the date and timeacquired in step S1805 is set in the Date Time 406 in the header as thedate and time of the edit start timing. The date and time of the movingimage recording start timing acquired in step S1804 are described in theDate Time Original 407. The recording processing of a thumbnail file 716as such management file is as has already been described above usingFIG. 6, and the generation date and time and update date and time storedin the directory entry are the date and time of the moving imagerecording start timing and the edit start timing respectively.

When acquiring the shooting date and time of the original image in stepS1804, it is often apparently determined that the shooting dates andtimes are not correctly set (e.g., “0” is set in the generation date andtime fields of the directory entries). In such a case, the systemcontroller 17 may acquire the contents of the update date and time field704 in the directory entry of the original image.

As in the first embodiment, the system controller 17 may use the DateTime Original 407 described in the file header of the original image forthe shooting date and time.

As described above, according to the first and second embodiments,unique file IDs can be assigned to still image files, moving imagefiles, and audio data files.

Application to the digital camera has been explained. However, thepresent invention can be applied to any device such as a mobile phoneand the like which have a data playback function.

As described above, according to the present invention, uniqueidentification information that does not cause any duplication can beassigned to data files.

According to the present invention, upon managing the reception state ofdata files using unique file IDs, efficient management with highreliability can be implemented.

Note that the present invention includes a case wherein the functions ofthe embodiments are achieved by directly or remotely supplying asoftware program to a system or apparatus, and reading out and executingthe supplied program code by a computer of that system or apparatus. Theprogram to be supplied in this case is that corresponding to eachillustrated flowchart in the embodiments.

Therefore, the program code itself installed in a computer to implementthe functional processing of the present invention using the computerimplements the present invention. Put differently, the present inventionincludes the computer program itself for implementing the functionalprocessing of the present invention.

In this case, the form of program is not particularly limited, and anobject code, a program to be executed by an interpreter, script data tobe supplied to an OS, and the like may be used as long as they have thefunctions of the program.

As a recording medium for supplying the program, the following media canbe used. For example, a Floppy® disk, hard disk, optical disk,magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape,nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R), and the like can beused.

As another program supply method, the user establishes a connection to ahome page on the Internet using a browser on a client computer, anddownloads the computer program of the present invention from the homepage onto a recording medium such as a hard disk or the like. In thiscase, the program to be downloaded may be a compressed file including anautomatic installation function. Also, the program code that forms theprogram of the present invention may be segmented into a plurality offiles, which may be downloaded from different home pages. In otherwords, the present invention includes a WWW server which makes aplurality of users download a program file required to implement thefunctional processing of the present invention by the computer.

Also, a storage medium such as a CD-ROM or the like, which stores theencrypted program of the present invention, may be delivered to theuser. In this case, the user who has cleared a predetermined conditionmay be allowed to download key information used to decrypt the encryptedprogram from a home page via the Internet. The user executes theencrypted program using the downloaded key information to install theprogram on a computer.

The functions of the aforementioned embodiments can be implemented whenthe computer executes the readout program. Furthermore, the functions ofthe aforementioned embodiments can be implemented in collaboration withan OS or the like running on the computer based on an instruction ofthat program. In this case, the OS or the like executes some or all ofactual processes, which implement the functions of the aforementionedembodiments.

Furthermore, some or all of the functions of the aforementionedembodiments may be implemented when the program read out from therecording medium is written in a memory equipped on a function expansionboard or a function expansion unit, which is inserted into or connectedto the computer. In this case, after the program is written in thefunction expansion board or unit, a CPU equipped on the functionexpansion board or function expansion unit executes some or all ofactual processes based on an instruction of that program.

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

This application claims the benefit of Japanese Patent Application No.2006-227021, filed Aug. 23, 2006, and Japanese Patent Application No.2006-227022, filed Aug. 23, 2006, which are hereby incorporated byreference herein in their entirety.

1. A data processing apparatus comprising: holding unit configured tohold device state information which is updated according to use of thedata processing apparatus and represents a use state of the apparatus,and device identification information unique to the apparatus; acquiringunit configured to acquire information associated with generation ofrecording data, which is different from the device state information, asrecording information, in association with the recording data;generating unit configured to generate unique identification informationof the recording data based on the device identification information,the device state information, and the recording information; recordingunit configured to record a file including the recording data and theunique identification information generated by the generating unit in arecording medium; and updating unit configured to make, when contents ofthe recording data are changed in association with the file stored inthe recording medium, the generating unit generate new uniqueidentification information, and to record a file including the changedrecording data and the new unique identification information in therecording medium, wherein when an edit operation for changing onlyattribute information described in a header of the file recorded in therecording medium is performed, updating of unique identificationinformation by the updating unit is inhibited.
 2. The apparatusaccording to claim 1, wherein the edit operation that updates only theattribute information described in the header is rotation processing ofan image.
 3. A method of controlling a data processing apparatus,comprising: a holding step of holding device state information which isupdated according to use of the data processing apparatus and representsa use state of the apparatus, and device identification informationunique to the apparatus; an acquiring step of acquiring informationassociated with generation of recording data, which is different fromthe device state information, as recording information, in associationwith the recording data; a generating step of generating uniqueidentification information of the recording data based on the deviceidentification information, the device state information, and therecording information; a recording step of recording a file includingthe recording data and the unique identification information generatedin the generating step in a recording medium; and an updating step ofmaking, when contents of the recording data are changed in associationwith the file stored in the recording medium, the generating stepinclude generation of new unique identification information, andrecording a file including the changed recording data and the new uniqueidentification information in the recording medium, wherein when an editoperation for changing only attribute information described in a headerof the file recorded in the recording medium is performed, updating ofunique identification information in the updating step is inhibited. 4.The method according to claim 3, wherein the edit operation that updatesonly the attribute information described in the header is rotationprocessing of an image.
 5. A computer-readable storage medium storing acontrol program which, when run on a device, performs a control methodaccording to claim 3.